Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
SRG-NET-000078-IDPS-000084 | SRG-NET-000078-IDPS-000084 | SRG-NET-000078-IDPS-000084_rule | Low |
Description |
---|
It is essential for security personnel to know what is being done, what attempted to be done, where it was done, when it was done, and by whom in order to compile an accurate risk assessment. Denied traffic must be logged. There may also be some instances where a packet that was permitted or other successful event (i.e., logon) should be logged to establish and correlate the series of events leading up to an outage or attack. Logging the actions of specific events provides a means to investigate an attack, recognize resource utilization or capacity thresholds, or to simply identify an improperly configured IDPS. |
STIG | Date |
---|---|
IDPS Security Requirements Guide (SRG) | 2012-03-08 |
Check Text ( C-43212_chk ) |
---|
Examine the aggregated sensor events log on the management console. View entries for several alerts. Verify the events being captured in the sensor logs include the success/failure of the action or request (e.g., login, permission changes) of each event. If the log events do not include the success/failure of the action or request (e.g., login, permission changes), this is a finding. |
Fix Text (F-43212_fix) |
---|
Configure the sensor log, so entries in the logs include the success/failure of the action or request (e.g., login, permission changes). |